The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Plan test effort and develop test strategy for an application software
|
|
Critically analyse functionalities of an application software from the system design document and create test strategy for new telecommunications product line Completed |
Evidence:
|
Produce steps for test strategy, including attributes of each step according to enterprise policy Completed |
Evidence:
|
Produce test strategy for evaluating suitability of application software for integration into telecommunications network Completed |
Evidence:
|
Critically analyse test strategy and identify types of risks that would hinder test performance or reality Completed |
Evidence:
|
Plan test strategy for regime
|
|
Produce phases of a test cycle for a test regime according to system design document Completed |
Evidence:
|
Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime Completed |
Evidence:
|
Evaluate features of testing tool and debuggers and select an appropriate tool to test software application and detect faults Completed |
Evidence:
|
Evaluate elements of test plan that cover testing functionality of the application software Completed |
Evidence:
|
Design test plan and produce test reviews
|
|
Determine forecast time, effort and cost for low and medium intensity projects to perform testing Completed |
Evidence:
|
Develop a test case or test scenario with prerequisite states based on requirements to generate expected test results for test plan Completed |
Evidence:
|
Produce test plan for specific phases based on requirements of project specifications for the application software Completed |
Evidence:
|
Produce test reporting associated with particular test phases within test plan Completed |
Evidence:
|
Critically analyse test reports and evaluate impact of test plan on the testing environment Completed |
Evidence:
|
Manage progress of test plan to minimise risks associated with testing and ensure test compliance with test requirements Completed |
Evidence:
|
Report any detected defects to product evaluation personnel, and prepare a strategy to manage defects Completed |
Evidence:
|
Manage test traceability
|
|
Create a traceability matrix to correlate relationship between marketing requirements and detailed requirements of software product to matching parts of design, test plan and test cases Completed |
Evidence:
|
Critically analyse testing metrics produced by test tool to manage tracking of defects and plan process improvements based on the metrics Completed |
Evidence:
|
Produce an evaluation report from traceability matrix to manage defects or failures from the test plan Completed |
Evidence:
|